Allow linking Plaid to an existing bank account and fixing existing Plaid connection - #98567

Explanation of Change

We're bringing Plaid reconnection/linking flow to NewDot in these cases:

1. Existing BBAs provisioned for the Expensify Card or BBAs on the Expensify Card waitlist that are not connected to Plaid → Needs linking Plaid to the account
2. Existing BBAs provisioned for the Expensify Card or BBAs on the Expensify Card waitlist with a broken Plaid connection → Needs re-linking Plaid connection (fixing)

Fixed Issues

$ #90572
PROPOSAL:

Tests

Test case 1: Link Plaid to an existing BBA

Precondition:

• Set up a bank account manually (not via Plaid) whose account number ends with 0000
• Workspace has requested to use Expensify Card (Go to workspace's Expensify Card page > Issue new card > Issue new card > "One more step" page shows)

1. Go to Wallet page
2. Verify the above bank account row appears like this:

3. Tap Connect
4. Verify the Plaid iframe opens
5. Proceed with the Plaid flow
6. Verify the success state shows
7. Verify the info box disappears from the bank account row on Wallet page

Test case 2: Fix (relink) a Plaid connection

Precondition:

• Have a bank account connected via Plaid whose connection is broken (mock data)
• Workspace has requested to use Expensify Card (Go to workspace's Expensify Card page > Issue new card > Issue new card > "One more step" page shows)

1. Go to Wallet page
2. Verify the above bank account row appears like this:

3. Tap Fix
4. Verify the Plaid iframe opens
5. Proceed with the Plaid flow
6. Verify the success state shows
7. Verify the RBR disappears from the bank account row on Wallet page

• Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as Test case 1: Link Plaid to an existing BBA

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If the PR adds or modifies the UI:
  • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
  • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
  • I verified all new/changed elements have meaningful accessible names and roles.
  • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

MacOS: Chrome / Safari

Fix connection

Screen.Recording.2026-08-24.at.22.09.09.mov

Connect to Plaid

Screen.Recording.2026-08-24.at.16.35.46.mov